Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)
Previous Next

not a issue

Well... after digging a bit more on the problem and searching for JSF documentation I realized the problem comes because the jsf/xsp environment runs different classpaths or threads. I was developing beans in Eclipse and pushing the jar's into the servers ext folder like I always did in previous versions of domino. It looks like the FacesContext doesn't run on the same thread as the classes deployed into ext folder. Something like that. I even tried to put the jsf jar's containing the FacesContext class into ext folder. Calling FacesContext.getCurrentInstance() the method was returning null.

The only way to solve this problem is to develop the classes inside the domino database where the FacesContext can be reached in the same thread. Now sometimes I'm facing the internal class loader error when changing my classes in the database. It look's like the server/database is not always aware of the changes in the classes. Sometime it runs the old code. Hope I can find why this is happening.

Thanks and hope this can help someone with same issues.
Jose Pinto


Feedback response number WEBB8BNDR8 created by ~Sean Fezkrotexettu on 11/29/2010

XPage Java User Bean and FacesConte... (~Sean Fezkrotex... 27.Nov.10)
. . not a issue (~Sean Fezkrotex... 29.Nov.10)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS